fix(gateway): verify effective provider transport before receiver operations - #5652

🤖 Generated by the Agentic Engineer

@coderabbitai full review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

🤖 Generated by the Agentic Engineer

cr:no-gate@18a6ff3 reason=service-failure

CodeRabbit declined this head's review because its included review quota is exhausted; its current-head response establishes the refusal. The reviewed artifact guard admits continuation and no findings were published. I am advancing to the next lane; no green review is claimed.

🤖 Generated by the Agentic Engineer

@codex review

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: 18a6ff35ce

🤖 Generated by the Agentic Engineer

Validation at 18a6ff35cef1c1dd75fe6650fc9042e281deb772: affected package tests with race detection, vet and lint pass; the deployment-order regression passes all 32 cases. CI 41276986362 is successful, and the native PR page confirms all required checks pass. Codex's current-head review is clean; complete conversation, review and inline-comment reads contain no unresolved findings. The newer main changes do not overlap this change, and the native merge state is clean.

The real provider observation remains unverified: its credential is available only in the protected deployment. Native HTTP controls establish request and failure boundaries but do not establish current provider state. The draft stays pending the narrow maintainer exception for one protected deployment trial; normal CI, queue and automatic recovery remain required. This change keeps transport disabled and does not complete #5448 or #5412.

🤖 Generated by the Agentic Engineer

At 18a6ff35cef1c1dd75fe6650fc9042e281deb772, current-head CI and the Codex review are successful; refreshed conversation, inline-review and thread inventories contain no findings. Native GitHub confirms all checks pass and no base conflict. Current main changes do not overlap the receiver implementation.

The maintainer has authorized one protected deployment trial of this head in the interactive session. This is the narrow readiness exception for the real provider observation, which requires the protected deployment credential; that user evaluation is still unverified until the trial runs. Promotion and queue checks, current-head validation and automatic recovery remain enforced. Forwarding stays disabled. Enqueueing will wait for the currently running production recovery to settle. This does not complete #5448 or #5412.

🤖 Generated by the Agentic Engineer

Merged as dbd0cd4d1a10896d293a07107eeb28e2f944fa64 after the protected deployment of reviewed head 18a6ff35cef1c1dd75fe6650fc9042e281deb772. Trial 41300692395 passed, including the production provider observation and four public-route probes. The selected fence was verified without another fence write.

The published manifest is sha256:24072cced11adde9c5e93e78fad0c601b549ee47aee60460a1d61be120592e03. Enforced deployment checks verified its signature, SBOM and provenance, and rejected an intentionally wrong signing identity. A fresh read-only production observation found that digest Ready in the source and all six root reconciliation layers, at their current generations. Validate Main, Code Quality and the main push checks passed; all 69 reported checks are settled without failure.

Separately, the existing live peer-refusal trial passed at 85671b538cd90b174a2441ff70030db7da6d80f1: ten direct TLS attempts were refused, both HTTP controls answered, and cleanup succeeded. Original-client transport, independent startup recovery and Email acceptance remain part of #5448.